Thanks for finding this. We have logged an issue for this problem and expect to deliver a solution in a future release.