Yep, this is a bug. It has already been reported (and fixed in our internal builds).