We're seeing this as well – it seems to be an active, unresolved bug