java:app resources can not be shared between ejb and appclient modules

use case:

1 ear composed of:
1 appclient module that defines 2 JMS queues (one in java:app, the other in java:global)
1 ejb modules with 2 MDBs (one listening to the java:app queue and the other to the java:global queue)

When the ear is deployed:
1. the ejb module is deployed, the MDBs are created and wait for the creations of their respective queues (defined in the appclient module)
2. the appclient module is deployed, its 2 queues are deployed
3. the appclient main is run

When the appclient uses the java:global queue, it looks it up, sends the message and the corresponding MDB receives it fine.
When the appclient uses the java:app queue, it looks it up, sends the message but the corresponding MDB never receives it
=> the MDB was never deployed because it did not see the java:app queue deployed from the appclient module.

Note that if I move the destination definitions to the ejb module, the MDBs are correctly activated but the appclient module is no longer deployed with errors:

[APPCLIENT-out] {"JBAS014771: Services with missing/unavailable dependencies" => [
[APPCLIENT-out]     "jboss.naming.context.java.module.simple-jms-appclient-test.appclient.env.jms.queueInGlobal is missing [jboss.naming.context.java.global.jms.queu
e.queue1]",
[APPCLIENT-out]     "jboss.naming.context.java.module.simple-jms-appclient-test.appclient.env.jms.queueInApp is missing [jboss.naming.context.java.app.simple-jms-app
client-test.jms.queue.queue2]"
[APPCLIENT-out] ]}

Steps to reproduce:

1. fetch git branch https://github.com/jmesnil/wildfly/tree/jms_appclient
2. build WildFly
3. run ./integration-tests.sh -Dts.basic -Dtest=org.jboss.as.test.integration.ee.appclient.jms.basic.SimpleJMSApplicationClientTestCase -DnoWebProfile