I'm sorry for the misleading comment.
In my setup this bug occured and after your comment I quickly changed my "FixedDefaultComponentSafeNamingStrategy" - but didn't disable it.
After cleaning up the db and the configuration, the bug doesn't appear anymore and the database schema gets created correctly.
From my point of view, the bug is fixed in hibernate 4.3.5.