Hi Luis,
This is related to a "fix" for another bug around OpenJPA and
temporary classloaders required for OpenJPA's dynamic byte code
enhancing. I use fix in quotes because it's one of those situations
where none of the solutions are perfect and each has it's own
drawbacks. For your 3.
Going to have to take a look at the app client deployment code again
and see exactly what is different. Any jar in the classpath that is
using the "Main-Class" attribute in the MANIFEST.MF is potentially a
java ee app client that uses annotations instead (or in addition to) a
META-INF/appl
