We've not found any workarounds for it. We have this logged as a bug to be fixed in the next release.

Thanks for the report and followup.

- Pete