The default flat class loading model seems to causing one mdb deployment to pickup msgs for other deployments of the same mdb class. Need to a test to validate isolation using class loader scoping.