Issue resolved,
>Use a 3-part (app_name/bean_name/remote) or (app_name/remote-bean_name/qualified_bean_name) EJB JNDI lookup instead of a 2 part (without the app_name prefix)
>The JBoss EAP server registers the following name
2010-03-22 11:07:33,326 INFO [org.jboss.ejb3.proxy.impl.jndiregistrar.JndiSessionRegistrarBase] (HDScanner) Binding the following Entries in Global JNDI:
TestRunner - EJB3.x Default Remote Business Interface
eclipselink-advanced-field-access-model/TestRunner/remote-org.eclipse.persistence.testing.framework.server.TestRunner - EJB3.x Remote Business Interface
2010-03-22 11:07:39,797 INFO [STDOUT] (WorkerThread#0[127.0.0.1:62483]) [EL Info]: 2010-03-22 11:07:39.797--ServerSession(4488512)--EclipseLink, version: Eclipse Persistence Services - 2.1.0.qualifier
>Use the name "eclipselink-advanced-field-access-model/TestRunner/remote-org.eclipse.persistence.testing.framework.server.TestRunner" in the JNDI context lookup to get an EJB @Remote @Stateless session bean $Proxy.
>Note: the name can also be "eclipselink-advanced-field-access-model/TestRunner/remote" if @Remote on the remote interface and @Stateless defaults are used without overrides.
>see
http://wiki.eclipse.org/EclipseLink/Bugs/305331
thank you
/michael
http://www.eclipselink.org