Could be. I'm fortunate enough that the company I work for at my day-job has a very explicit clause in their "IP Assignment Agreement" that spells out - very clearly - that if you invent something on your own time, on your own equipment, that doesn't involve company IP / knowledge / etc., then they make no claim to it. Now, granted, the way the legal system works in the US, they could - if they turned evil - turn around and try to claim ownership of some of my open-source stuff, and the outcome would (as always) come down to "what a particular combination of judge, jury, & lawyers, in a particular situation, on a particular day, decide." But given how clear they are on this point, their chances of successfully claiming such ownership seem pretty low.
From what I've seen/heard, it's not uncommon for such clauses to exist... some companies also invite you to submit a list of "things that you were already working on before gaining employment here" that are excluded from any IP claim by $COMPANY. Lulu, for example, did this when I was there (and presumably still do). When I joined them, I just gave them a list of every open-source project I'd ever touched, looked at, thought about, or considered, and the vaguest most abstract list of things I was working on that I could dream up. They weren't exactly crazy about the list I gave them, but it wasn't a deal-breaker. <shrug />
It sucks that we have to deal with this crap at all, but I honestly don't think most employers are actually evil in this regard. A lot of this is just bureaucracy for bureaucracy's sake, IMO.
I would estimate that a majority of developers are under pretty onerous agreements that assert control over all inventions that they create while under the employ of the company.
Before my startup days I was faced with such an agreement. The lawyer I consulted with (in Texas) certified that these agreements are in fact legal and have been upheld in court. Apparently California is more employee friendly in its labor code.