Thank you for reporting this issue.
It appears this is a bug in JustMock 2013 Q1 SP2 which has already been fixed. The fix will be included in the upcoming internal build due this month. An internal build is a preview of our upcoming major release - Q2 2013. So please give it a try once it's out and let us know what your feedback is.
I hope this information helps.