Apple certainly doesn't deserve being defended in this case, but I did want to throw in my two cents as a former quality software engineer and long time sufferer of this disappearing mouse problem.
First as I look at this thread there are 280 replies which probably means there are two or three dozens commenters. Apple undoubtedly has metrics that allow them to see how long a thread is or how many users comment on an issue and can predict how widespread the problem is and how many people it affects. With two dozen commenters it's likely we haven't met their threshhold for raising alarms.
Second as a QA guy I feel for these troublesome bugs. Testing is a lot like the scientific method. They make a hypothesis, establish a control, alter a single variable, test and monitor, rinse and repeat. These complex bugs that only happen on occassion and are caused by 3rd party software conflicts, but only for some people are extremely tough to sort out. It's possible the QA team hasn't been able to reproduce this issue, or they can't reliably reproduce it. Then if the QA team is finally able to reliable reproduce it, it may stump the developer and they may not be able to pinpoint where in the code things are going awry.
So I know it's all been a frustrating issue that's been a pain in my side for a good long time and I can understand your frustrations as well, but consider the scale that Apple operates at today and the complexity of what they are doing and it's a miracle any of it works at all. Apparently nobody lived through the days where Microsoft was king and Windows 98 was endemic and getting a printer to actually print often took days of troubleshooting.