For the complaints about datasource / memory leak it's explained here:
http://stackoverflow.com/questions/3320400/to-prevent-a-memory-leak-the-jdbc-driver-has-been-forcibly-unregistered
so I guess this SEVERE message can be simply ignored.

As for the "Could not load com.mysql.jdbc.ProfilerEventHandlerFactory" this is because we bundle mysql driver with the application itself. Normally this should go to the server/lib folder insteead. Once we are done with the tests Arquillian is undeploying the whole WAR so the driver is gone and hence TomEE is not able to properly unregister the datasource. But as the exception message says - it has no functional impact. I would simply ignore it.