Because they can just... stop maintaining it if they wanted. They are completely free to do so.
Many developers like to feel useful, feel like they are solving an important problem in a suitable way. Some even want the fame associated with it, or the doors having such (a) project(s) opens (you use X? I wrote it, and maintain it - or people hunting you specifically because you are known to have created X).
The point is, the tradeoff between the feeling of being taken advantage of and feeling useful and fulfilled because of solving an important problem in a suitable way is controlled directly by the author / developer! If they feel it is not worth the effort, they can just stop!
Having a permissive license helps you gain popularity. Many people won't touch GPL derivatives for their business / side-project-that-might-turn-into-a-business so such a license can have an inhibiting effect in adoption. Developers generally aren't stupid, they know that and they choose more permissive licenses, because they want to be seen, they want their solution to be used. They maybe want the fame and open doors associated with having such a project take off. It is a trade-off under their control. They can stop with maintenance any time. Hell they can even change the license of future versions (if they have not started with a GPL-like license) if they want. So I don't see the problem here. Everything is under the developer's control. You can't have it both ways: The boost to popularity by having a no-strings-attached license, but reaping proportional profits from such an endeavor as if you had a restrictive license protected by a business entity.
If you give money (value) away for free, you'll be pretty popular. "I want to be easily popular as if I'm giving money (value) away for free, without actually giving money (value) away for free" does not make much sense.