Note: for some reason that is beyond me, I only encounter this problem during execution of testcases. It does not happen during a deployment in WildFly, so it could be somehow related to the classpath or something..

It should be possible to reproduce it with the attached test application though.