It is a start. It tells us what the two separate classloaders are that defined the entity. The EarClassLoader is where application classes should be defined. Next question is which aggregate classloader is defining the entity, the TcclSafeAggregatedClassLoader or AggregatedClassLoader?

It might be helpful to have a textual description of the involved classloader implementation classes (including their parent class and referenced classloaders).

Would also be nice to have the call stacks for the two locations (EarlClassLoader/aggregate classloader) that are loading the same entity class.

I think that will give us enough information for GlassFish. We probably will need the same for Tomcat as well. Perhaps then, we might see the problem or have enough information to ask the "JBoss classloader" expert, which would be dmlloyd.

Would be interesting to know if this problem recreates on WildFly 9.0 (http://wildfly.org has the download if someone can try).