RIM has told us this is fixed in the next version(s) of software that has been released to the carriers for their certification process. In addition, they have told us they will not mark it as resolved in their knowledge base until the fix is publically available.

RIM's escalation team has assured us that this will be fixed in a maintenance release of the 4.2 OS as well as the 4.5 (formally known as 4.3) release.
We won’t know until we see the software, but like the rest of the world, we are anxious to get our hands on the 4.5 OS. Rest assured we’ll be testing this first thing when it is released.

If anyone experiencing this issue gets their hands on a beta release of this code, please report any findings.