After tidying up sample-bindinds.xml in JBPAPP-996:

The file correctly refers to JMSProviderLoader in the 'jboss.mq' domain, as this is the default messaging provider in AS 4.2 / EAP 4.2:
<service-config name="jboss.mq:service=JMSProviderLoader,name=HAJNDIJMSProvider"

In EAP 4.3 this needs to point to 'jboss.jms' for all 4 occurences in the file:
<service-config name="jboss.jms:service=JMSProviderLoader,name=HAJNDIJMSProvider"

If the file is patched for producing EAP 4.3 then you can do it there. Otherwise I suppose you can add duplicate definitions using both domain names.