This should already happens in tearDownAfterClass(). Do you remember, we had a similar issue on Oracle the last time we met in Stuttgart. @butonic debugged it and found out that the problem was a db query to delete the user, if I remember correctly. Maybe we re-introduced this bug or a similar one by accident?