It is also not that clear all of the algorithms are fully original clean-room implementations written by the authors --- the techniques in the book are well-known and previous implementations do exist, written by other academics. As such, claiming copyright on some the codes is not morally defensible, even if legal.
It's just better to not read the book at all. Since you cannot use the codes as is, if you want to learn about the theory behind it, it's better to pick a different book.
In my experience and opinion, Numerical Recipes hits a pretty unique spot by explaining enough about the ideas behind and how the algorithms work, that one can start implementing them (with or without reading the code) but not getting theory-heavy and full of equations and proofs, like a real numerical analysis textbook.
Kahaner, Moler, Nash: Numerical Methods and Software is a similar book, maybe even better, but it's from 1988 and never updated, and it's not nearly as widely known. Also it covers a smaller range of topics.
For anything to be used in the real world, in production, you're better off taking code from somewhere else.
What alternative to use depends on the topic/algorithm in question. But NR should just be a starting point, not what you actually use.
First, I think the publishers started to see that there was money to be had as the copyright/left wars took off and the book left academia (where you weren't going to get any money suing them anyway).
Second, as the web grew (late 90s) "programmers" started just copy-pasting "code"/html from wherever they liked without understanding or attribution, and that is something that still exists today... although I hope that more people recognize it as a problem to be stamped out.
So now, NR is somewhat of a relic that oldsters remember as a useful tool, and a new generation see as another symbol of a problem they're trying to get rid of. It's really both.
And they're code doesn't exactly conform to best practices anyway, so if it's small (e.g. a random number generator), then implementing it yourself is a good idea. And if it's big (e.g. nonlinear optimization), you should use some other off-the-shelf implementation anyway, and just use NR to understand the theory behind it, strengths/weaknesses, etc.
From the book:
Copyright does not protect ideas, but only the expression of those ideas in a particular form. In the case of a computer program, the ideas consist of the program’s methodology and algorithm, including the necessary sequence of steps adopted by the programmer. The expression of those ideas is the program source code (particularly any arbitrary or stylistic choices embodied in it), its derived object code, and any other derivative works.
If you analyze the ideas contained in a program, and then express those ideas in your own completely different implementation, then that new program implementation belongs to you.