http://lists.jboss.org/pipermail/wildfly-dev/2013-July/000466.html
contains the details about deployment level classes are leaking (CDI
beanmanager passed into deployment, bean validation factory, others...).
In WildFly 8, We do have a
META-INF/services/org.hibernate.engine.transaction.jta.platform.spi.JtaPlatformProvider
file that contains org.jboss.as.jpa.hibernate4.DefaultJtaPlatform
The org.jboss.as.jpa.hibernate4.DefaultJtaPlatform is a system module
class but could also be an application deployment class.
Question: Do we have a way to unload services that have been loaded
when the original classloader (deployment) is no longer needed (e.g.
when SessionFactory is closed)?
I'm not sure that would help for the leak that I am reproducing which
could be a different problem.
By the way, this is with Hibernate ORM 4.3.0.Beta3.
Scott