I'm really not sure what you're getting at with your 'viral and inadvertent' comment - it almost seems like you're willfully ignoring the points being made in reply to your comments.
Additionally, I posted a few examples below where otherwise responsible contributors to a codebase might leak some GPLd material into the codebase. Over a long enough time, with enough developers contributing to your codebase, it's inevitable.
"Not distributing your program", for a business, may mean a lot of money. It might mean bankruptcy. How do you know it will be affordable to replace the offending code? The author said "inadvertent", not "tiny".
That's the viral part. GPL source code is all over the net. Any developer on your staff could look at something on line and derive some code from it, and drop it into your codebase. You'll never know about 99.9% of it.
Incompetent programmers do that too.
> You'll never know about 99.9% of it.
Too bad if it's your job knowing it.
Thankfully, copyright does not protect ideas, only the expression thereof. In this context I take the word "derive" in an informal rather than legal sense (i.e. "derivative work"). If there's only one way to, say, clear the non-blocking flag of a file descriptor, save a couple of variable names, then a developer finding that one way in some example code online and using that method in their own code can't reasonably be considered in violation of copyright law or any license.
NB: IANAL.
Well that's what's so crucial about having solid Best Practices and hiring good developers. If you hire people who break the rules (deliberately or accidentally, with your knowledge or without), then there's your problem. The GPL has nothing to do with that scenario, it's you hiring people who can't toe the line.
You're correct that other open source licenses can present similar issues of poisoning.