The auto creation of destinations for MDBs is broken in AS trunk with HornetQ. The org.jboss.as.integration.hornetq.deployers.DestinationFactoryDeployerPlugin responsible for creating the destination has multiple issues:

1) It uses the "destination" activation config property as the destination name and then creates a jndi name for that destination. This is incorrect because the "destination" activation config property itself is the jndi name.

2) This org.jboss.as.integration.hornetq.deployers.DestinationFactoryDeployerPlugin along with the CreateDestinationDeployer creates a JMSConfiguration as an attachment to the deployment unit. If there are more than one MDBs which require creation of destinations, then this deployer ends up using the same attachment name for both the attachment names, ending up the "last one is the winner" scenario.