I once named a project KERBCRaWL, safe in the knowledge that it was unlikely to be an acronym in general use.
I've found this problem usually crops up after the first iteration of a codebase. You've picked your package name and then someone in sales gets to see the user interface and suggests a new name for the product. You can't win!
Having names like Badger, Pluto and Wombat is at least a shallow learning curve. The problem arises when you can't form a glossary around the names because the system functions aren't clear (ie, a new service should have been introduced)!
E-mail addresses are not publicly displayed, so please only leave your e-mail address if you would like to be notified when new comments are added to this blog entry (you can opt-out later).