Would you create a hundred lines in a text file though?
There is perhaps a psychological hurdle of thinking in terms of the text entries in your binder outline as being files. It would of course be absurd to create hundreds of actual files on your computer for a glossary, but nothing in Scrivener really maps to that specific concept internally. I would go so far as to say that it is rather unfortunate, and perhaps ultimately confusing, that we refer to the indented lines in the binder outline as “documents” or “files” at all, never mind “folders” being in the mix too. It just brings a lot of Finder/Explorer based mental baggage over that is wholly irrelevant, and in fact largely fictional.
Indeed, if you don’t type into the main editor, they never even become actual files at all, they are in essence much closer to my original assertion: they are in fact lines in a file—the binder file in this case. But really you shouldn’t concern yourself with whether your use of the binder’s features generates literal files or not—Scrivener can take it, and it’s probably making more files than you realise all the time (like how typing into index cards creates .txt files, and using a style creates a file for every chunk of text you use styles in, etc.).
I have projects with many tens of thousands of literal files in them, which map back to binders that have thousands of entries. It doesn’t break a sweat, and it won’t even notice your list of several hundred. 
Seriously, the only time I’ve encountered a case where someone had “too many lines in the binder” is a project we were sent in where it looked like the user had tried to download vast chunks of Wikipedia into the project, and had hundreds of thousands of entries. Even then, it was more a case of how much the computer could handle, rather than the software itself. It was handling it just fine, only very slowly, because that’s an idea perhaps better deferred to 2035’s hardware. 
Anyway, if you want to see a real-world example of this in play, download the Scrivener user manual project and jump down to the Menus & Keyboard Shortcuts appendix. You could turn on View ▸ Outline ▸ Show Subdocument Counts in Binder as well, but with a little poking around, you’ll see that this 71 page appendix, which is incidentally formatted much like a glossary would be, is in fact comprised of over 500 “files”—one for each command! Overall though, the structural design of that project should serve as a demonstration that the binder is a large-scale hierarchical outliner not a file manager, and it is meant to be used as such.