My logs are seeing a lot of these errors. I'm running 4.2 multisite and the last update to jetpack. A similar error was reported a year ago but reported as fixed. Seems it wasn't really fixed or made its way back.
Apr 24 07:56:51 ip-10-0-0-6 mysqld: 150424 7:56:51 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: DELETE FROM wp_options WHERE option_name LIKE 'jetpack\\_nonce\\_%' AND CAST( option_value AS UNSIGNED ) < 1429858611 ORDER BY option_id LIMIT 100
Apr 24 07:59:38 ip-10-0-0-6 mysqld: 150424 7:59:38 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: DELETE FROM wp_options WHERE option_name LIKE 'jetpack\\_nonce\\_%' AND CAST( option_value AS UNSIGNED ) < 1429858778 ORDER BY option_id LIMIT 100
Apr 24 08:01:42 ip-10-0-0-6 mysqld: 150424 8:01:42 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: DELETE FROM wp_5_options WHERE option_name LIKE 'jetpack\\_nonce\\_%' AND CAST( option_value AS UNSIGNED ) < 1429858902 ORDER BY option_id LIMIT 100