I wholeheartedly agree with Lee. And the n3rdling tells us in the comments that Firefox has a pref to prevent this occurrence from happening. I hope this is something Dave & Co. can cook in to a future rev of Safari.