The workaround I ended up using was not something I was happy with, but this was for a small internal project so it was good enough for me. As I said at the time the solution is "a bit dodgy", and I offered the diffs for the jTDS source but nobody has asked to date. I may still have these somewhere, but they will be for an out of date version of the driver by now.
I'd suggest contacting Adobe support if you have an agreement in place, perhaps there is a patch or better workaround than I could come up already available.
Altering the database driver is really not ideal, and if the source to SQLAssembler was available I believe it should be fairly simple to implement a workaround there.
It may also be worth confirming this still occurs in version LCDS 2.6.