Database Logon Error When Multiple Reports ran through single IIS process

So using the latest SP, when multiple versions of my app are being called upon through IIS, which means multiple .rpts, I get intermittent database logon errors. (I can run my app through IIS via a webservice in a "batch" mode). I'm using the ADO xml push method to send data to the crystal report.

However, I noticed something peculiar. If I hard code the path of the data xml or leave it blank as the only datasource connection, the intermittent errors are no longer replicatable.

So it looks like crystal occaissionally  will mix it's data source locations and pick the wrong one when multiple crystal reports are being called within the same process. Which is peculiar because as my code sample shows, we pass an xml data structure to crystal at runtime. It shouldn't matter what source xml is specified in the .rpt at creation time, as long as it is the same exact schema i'm passing at runtime.

l_objReportDocument.Load(l_strReportFileName)

                l_objReportDocument.SetDataSource(l_objDataSet)

                ' create the report options

                Dim l_objExportOptions As CrystalDecisions.Shared.ExportOptions

                l_objExportOptions = l_objReportDocument.ExportOptions

                l_objExportOptions.ExportFormatType = CrystalDecisions.Shared.ExportFormatType.PortableDocFormat

                l_objExportOptions.ExportDestinationType = CrystalDecisions.Shared.ExportDestinationType.DiskFile

                l_objExportOptions.DestinationOptions = New CrystalDecisions.Shared.DiskFileDestinationOptions()

Here is the previous thread where I talk about what I'm seeing.

Database logon Error Through IIS

Is there a way I can get crystal to truly ignore that datasource location? Somehow clear all datasource locations at runtime perhaps?

I tried

l_objReportDocument.DataSourceConnections.Clear() (or something like that) with no luck.