Update:
This is a known issue, internally, and has an associated bug filed, with a high priority assigned to it.