The EJB v. 3.1 Specification fills this gap defining, in its own words:

If.
Module
Names in the module namespace will be accessible only to code within the same module and conform to the following syntax:
java:module/<bean-name>l[!<interface-fqn>]
Once more, each path fragment retains the same meaning described for the global namespace JNDI names.
The same publishing rules for a compliant container described in the global namespace section.
Local Clients
It may be important to notice that, although global JNDI names for local interfaces (and no-interface views) are published, this does not imply that such an interface will be accessible to components running in another JVM.
Conclusions
Reference: EJB 3.1 Global JNDI Access from our JCG partner Grey at the The Grey Blog.