That's actually the best move. SET ENGINEBEHAVIOR was most likely put in because of the changes and so developers did not need to right away change their SQL statements, but it's more of a bandaid than anything else. I would highly recommend changing your SQL Statements to work with the new behavior.