Actually thinking about this, both (or all) of these things should just work out-of-the-box,
if you have all compatible components.
If it doesn't work, then it's probably not CL issue, but Hibernate components incompatibility.
ear and war should both already have parent-first=false lookups:
* ear by that isolation flag in EARCLDCeployer
* war by the spec
I know we have tests for this in our testsuite, hence I doubt this is CL issue -- I still could be wrong.
Whereas Hibernate had its components issues.