Errr ... hard to do ... sight unseen, don't you think? Can't do Vulcan mind melds from here! ;)
Maybe a true DB admin person would step in and confirm/correct, but from what I understand, the temp tables are supposed to be cleaned up ... ie, all rows removed and the table itself removed when whatever process is done with them. That doesn't happen IF there are LOCKS on those tables. Since I've never experienced the same problem I've never seen tmp tables in the DB so don't know if there is a naming convention of some sort or not.
With some mysql tools or from command line, one could inspect the contents of those tables and then make a pretty good educated guess.
Some technical info concerning temp tables can be found at:
http://dev.mysql.com/doc/refman/5.1/en/create-table.html
Section on temp tables says:
Temporary Tables
You can use the TEMPORARY keyword when creating a table. A TEMPORARY table is visible only to the current session, and is dropped automatically when the session is closed. This means that two different sessions can use the same temporary table name without conflicting with each other or with an existing non-TEMPORARY table of the same name. (The existing table is hidden until the temporary table is dropped.) To create temporary tables, you must have the CREATE TEMPORARY TABLES privilege.
Note
CREATE TABLE does not automatically commit the current active transaction if you use the TEMPORARY keyword.
Note
TEMPORARY tables have a very loose relationship with databases (schemas). Dropping a database does not automatically drop any TEMPORARY tables created within that database. Also, you can create a TEMPORARY table in a nonexistent database if you qualify the table name with the database name in the CREATE TABLE statement. In this case, all subsequent references to the table must be qualified with the database name.
Ok, since we are both now into un-charted waters here, suggest making a backup of the DB (sql dump) and then go about removing those tables ... maybe one at a time. Before you do, make sure you know how to restore that SQL dump to get the site back should removing one of those tables does something.
'spirit of thinkering', Ken