Description of problem:
The re-activation on hornetq, is using the wrong classLoader.

This is because a new Thread is started instead of using the WorkManager from the ResourceAdapter.

How reproducible:

You could visually verify the classLoader used. This had issues in production for a customer after failover, and we couldn't replicate the exact classNotFoundException they had but we could assert the wrong classLoader i used.