Comment 6 for bug 1539504

Steps to reproduce in comment #5 can be reproduced even in upstream MySQL 5.6/5.7, hence marking this as "confirmed". Will need developer comments on this.

http://dev.mysql.com/doc/refman/5.6/en/replication-rbr-usage.html
In MySQL 5.6, you can switch from statement-based to row-based binary logging mode even when temporary tables have been created. However, while using the row-based format, the MySQL server cannot determine the logging mode that was in effect when a given temporary table was created. For this reason, the server in such cases logs a DROP TEMPORARY TABLE IF EXISTS statement for each temporary table that still exists for a given client session when that session ends. While this means that it is possible that an unnecessary DROP TEMPORARY TABLE statement might be logged in some cases, the statement is harmless, and does not cause an error even if the table does not exist, due to the presence of the IF EXISTS option.

Reporters affected by this bug are basically asking if there is something that can be done to avoid errant GTIDs on the slaves.