We need to re-package our JBoss AS services so that they properly contain the classes the create, do not leak the class they import and properly define what classes they want to export. All of this is possible thanks to the new JBoss MC classloading features.

Also, most of the classes in the JARs in /lib are not at the proper location there and should instead be incorporated in their related service in /deploy instead of poluting the global class space. lib might end up containing only the global meta-model classes as well as MC-extensions (deployers, etc.)

Today, it contains all of this (mess):
> cache-invalidation-service.xml
> cluster
> deploy.last
> ejb2-timer-service.xml
> ejb3-connectors-jboss-beans.xml
> ejb3-interceptors-aop.xml
> ejb3-timer-service.xml
> hsqldb-ds.xml
> httpha-invoker.sar
> iiop-service.xml
> jboss-local-jdbc.rar
> jboss-xa-jdbc.rar
> jbossjca-service.xml
> jbossweb.sar
> jbossws-container-jboss-beans.xml
> jbossws.sar
> jms-ra.rar
> jmx-console.war
> jmx-invoker-service.xml
> jmx-remoting.sar
> jsr88-service.xml
> juddi-service.sar
> mail-ra.rar
> mail-service.xml
> management
> messaging
> monitoring-service.xml
> properties-service.xml
> quartz-ra.rar
> remoting-service.xml
> ROOT.war
> schedule-manager-service.xml
> scheduler-service.xml
> security
> snmp-adaptor.sar
> sqlexception-service.xml
> transaction-jboss-beans.xml
> transaction-service.xml
> uuid-key-generator.sar

See related JBAS-5955 and http://lists.jboss.org/pipermail/jboss-development/2008-September/012457.html