This behavior has been standard for MySQL and hibernate from the beginning. I belive the MySQL driver interprets a database schema the same as an Oracle catalog .... but a MySQL catalog has subtle differences from a schema and does not play well with hibernate.
My standard fix up (workaround) is to immediately remove the catalog property. I most frequently use Forge to reverse engineer and generate a CRUD webapp ..... so it's become routine for me. Thanks to Eric for reporting the issue .... I should have done so long ago.