It could be, but I also have used these in places where we weren't sure of the domain model for an entity. The business is a little flaky, and they want a couple random attributes that vary for customers. If it's low volume, like settings for a client, I've done this before. We've had a case where this was loaded once by each client in a session, and there were a few settings they wanted for some, but not for others. Since it was a rapidly changing set of requirements, making constant table alterations and having a wide table of settings didn't make sense. Simpler and easier to EAV these.

Of course, we had to convince the developers to "reload" these settings in the app if the client changed things. For some reason they thought forcing a client to log out to get a new setting that changed was a good idea