Hi Ryan,
I afraid this is a bug for jBPM-4.3. We try to resovled it in the jBPM-4.4. But there is no SQLServer environment in QA, So we can't be sure that this problem had been resovled in SQLServer environment. If you could test it in jBPM-4.4, it will be very apprieciated. Thank you very much.