Want to run two instances of same Assembly but with different binding information

I have an assembly with many orchesrations associated with the assembly. The orchestrations use the MQ Adapter to read and write messages to a set of MQSeries queues. One Orchestration writes a message to a send port and using the MQ correlation id, reads its specific response from the recieve location. Another Orchestration waits for any message to arrive on another revieve location. Basically we have one Orchestration processing Request/Response processing and the other processing data being pushed to the application.

 The problem is we have one computer supporting our Integration (INT) and Qualification (QT) testing. For the request/response procesing there is no problems since the correlation id allows the INT and QT applications to read only thier messages. The feed processing is the problem. The incomming message is picked up by BizTalk, procesed and placed into a queue for the application. Since both the INT and QT applications read from the same queue they fight over the feed messages since there is nothing to identify who it belongs to.

 What I need to do is install the same assembly twice, once with the bindings file configured to talk to one queue manager and its set of queues and a second instnace of the assembly configured to talk to a second queue manager and its set of queues. This would allow the INT application to connect to one queue manager and recieve feed data and the QT application to connect to the other queue manager and recieve its feed data.

If I had two computers, I could do this easily but since they both must exist on the same system I am having problems. I figured I could create a second host instance (intBizTalkServerApplication and qtBizTalkServerApplication). This would allows me to install the Receive Locations and Orchestrations in the second host instance but it appears the Assembly gets loaded via btsdeploy into a common area so the second time I attempt to deploy in the second host instance it gets an assembly already deployed.

 Basically I need two fairly exact copies of the assembly running but with different assemblies so the Receive and Send ports talk to a different queue manager.