Not sure why this happens yet, but we've come up with a workaround that we hope will help. Will show up in the next 4.3 and 4.2 bugfix releases.
