Thanks! We've logged this bug!
Now fixed - you should see it in the next patch :) Thanks for reporting, though - that's how we were able to jump on it so fast!