I've confirmed that this is a bug in 03.00.01 and marked the issue as such. I don't know when we'll be able to fit a fix for it into the development cycle, but if you're able to fix it, we'd love to accept your pull request.