microsoft reports that this bug was identified and fixed in the latest 2008 R2 SP2 cumulative update (CU13, build 10.50.4319.0, see http://support.microsoft.com/kb/2957174 for details).

we're currently on 2008 R2 SP2 CU7, so it looks like catching up on the CUs will resolve the problem for us.