My guess is that 10.5.7 may have installed an older version of Webkit which didn't have this issue. The new Safari, obviously, updating it to the newer revision, which like the one in the last beta, has the issue.