Him: I can explain why this would be a challenge to fix, if you need some clarification.
Me: Yes, please!
Him: Alright, the problem stems from the fact that it's both launching on the 22nd, and each team has had to write their system to write their party system to handle party hand-offs from the OS side. So if you change the way the way the system handles matchmaking or parties or voice chat in parties or voice chat in games, you run the risk of breaking every released game's individual API, because you have to account for how each individual game's XBL functionality is written. However, the way it is now is a huge cluster mess of probs.
So, in a weird way, they can't fix it on the OS side. What you could do is you could write an all encompassing XBL-API and hand it to each dev. But then you'd have to make that the standard, the OS side would have to be patched to recognize only api handshakes from the game to the OS with that particular code. Meaning some games would still end up breaking, but it'd be fewer. And it'd be more future proof.
No word on what MS is going to do about it though, and with the trouble they are having pushing online clients to Thunderhead to begin with.
They have bigger fish to fry if they want their next 6-months of titles to launch on time.