No, I meant the EJB JARs - JARs that are EJB modules within the EAR. The EJB JARs in GlassFish 2 are added to the class path for the app client during an appclient command. This is because some developers did not declare that their app client modules depended on EJB JARs. (Ideally the app client would depend only on the interface but not everyone wrote that way.)
Java EE 6 spec changes impose stricter enforcement of class path handling so as of release 3 GlassFish no longer does this.
- Tim
[Message sent by forum member 'tjquinn']
http://forums.java.net/jive/thread.jspa?messageID=470559