The full bug report is here: http://jira.jboss.com/jira/browse/JBSEAM-3049

Basically, in 2.0.1, the getClassMetadata (used, among other cases, during the activation of passivated entites in the infamous MEI interceptor) uses Seam.getEntityClass to find out  the entity class for a passed bean, while in 2.0.2 (both GA and SP1) it switched to use its own getEntityClass method, which internally uses Hibernate.getClass. The difference is that the latter method would stumble on a non-existent entity, throwing a javax.persistence.EntityNotFoundException, while the former would handle this case just fine.

Now, was there any particular reason to switch to the latter method from the former one?