Because they have fewer people working on the product? I don't know. But presumably they have some constraints on resources that prevent them from doing everything -- hence having to prioritize.
Surely that perception hurts them more than the cost of a few developer-months to take one of their existing spellcheckers and drop it into IE?
So then what do you cut? Dev/test time doesn't just appear magically. Do you cut flexbox? Text shadow? History?
Everything is about tradeoffs and constraints. You may not be familiar enough with the industry to know that they're there (ppl think that MS and Apple have enough money to simply do everything, but they don't), but trust me, these products have serious resource constraints across the board.
I'm not asking or expecting them to support everything and anything with their minuscule bank account and negligible market power. I'm just pointing out that the web is kryptonite to Microsoft and their PR to the contrary is laughable. If you want to believe it's simply mismanagement on a massive scale that leads them to fail at the web year after year then good for you, but I personally think it's just smart self-interest on their part.
I suspect it may have more to do with the fact that some features are easy to do as addins. There are several spell checkers available for IE. Given that the IE team seems resource constrained, it seems more useful to work on things like perf, compliance, security, than features that are easy to add by 3rd parties. I'm not saying it wouldn't be nice to have, but given that IE9 still has HTML/CSS gaps, I'd much rather they work on those.