I once created a PHP framework called RocketSled because it was “the fastest thing on rails” and that gave rise to somewhat whimsical but also descriptive names on the same theme:
RocketPack: package manager
DataBank: caching auto loader
Murphy: automated testing
Each of those modules is named quite specifically but that’s because they do one thing.
I created an ORM tool called PluSQL, because it’s not an ActiveRecord style ORM but adds a bit on top of straight SQL statements. General enough that if I want to enhance the functionality beyond ORM I can, but also pretty easy to remember what it does from the name.
The one library I created that may suffer from the problem described is Trellinator, which I recently began updating to work with the WeKan API, so maybe that should have been Kabanator … there’s still time.
But I don’t think calling them all after my favourite Futurama characters would have been a better choice.