My solution is to extend DBTestCase to make sure it spins up a hibernate session the first time DBUnit is used.
Note that I close the session so if you are using create-drop I dont think this will help as is.
Also note that this code will not run as-is since it includes the code for running an additional setup step . This takes a single DBUnit xml file and runs it to delete the data in the database. The reason for this is that DBUnit gets its knickers in a twist with the table orders when deleting tables with foreign keys, this table allows you to specify a different delete structure. See this post.