The physical bean mappings of EJB dependencies, whether those dependencies are declared
using @EJB or ejb-ref in .xml, are resolved at deployment time, so there's no portable way to
have glassfish do this for you automatically. You can always do a runtime lookup of a bean for
more dynamic behavior. The way in which you discover the global JNDI name of the target bean
is left up to your application.
[Message sent by forum member 'ksak' (ksak)]
http://forums.java.net/jive/thread.jspa?messageID=315070