Someone should really delete !!!StandaloneLibraries from the SVN... all it does is confuse newbies.
Anyway, if you run standalone libs, when you disable an addon, there's no need to disable its libs as well; 99% of libs are load-on-demand, which means that even if they're left enabled they won't be loaded unless an addon wants to use them. There are a few exceptions to this. All of the frameworks (Ace2, Ace3, Rock-1.0) are always loaded, and so are "libs" like LibHealComm-3.0 and Threat-2.0 that still do stuff (i.e. broadcast your heal cast data or threat data) even without an addon providing a frontend for the user.
Generally you'll always need your frameworks enabled, uunless you only use a few addons and are sure that none of the currently enabled ones need, say, Rock (you can test by disabling it and seeing if any addons error out) in which case you could disable it if you really wanted. HealComm and Threat you can disable if you're not currently using an addon that requires them (again, if you're not sure, disable and see what complains). Most everything else you can just leave enabled all the time, because it won't be loaded anyway if nothing's using it.
If you want to see which libs you can delete, install something like ACP or OptionHouse, and after you've been playing for a while in various situations, take a look at which libraries are still marked as "Loadable on demand", i.e. not yet loaded. Those are probably safe to delete. And if you delete something that ends up being needed, it's not like you can't install it again in about 30 seconds. :P
Thanks this is the kind of response I needed... I didn't realize most of them don't actually load anyway if they are enabled unless a mod needs them. I use a lot of different chars and some of them use mods that others dont so I wanted to make sure I wasn't loading stuff I didn't need.
Any i just mentioned !!!Standalone because i remembered it from long ago, its probably not even there anymore as people have said.