Sure, it's cute, but maybe in this case ListItemRemover might be a better name. I've seen Monty Python's The Holy Grail, but it may take me a while to realize what you are meaning to do. I've seen other similar cutesy namings fail. Given the choice, choose clarity over entertainment value. It's a good practice.
Most meanings have multiple words.
For instance, it's confusing to have fetch , retrieve and get as same-acting methods of the different classes. Sadly, you often have to remember who wrote the library in order to remember which term was used. Otherwise, you spend an awful lot of time browsing through headers and previous code samples. This is a considerably worse practice than the use of encodings. Likewise, it's confusing to have a controller and a manager and a driver in the same process.