The issue seemed to go away on its own. At some point the libraries page started showing what was getting installed to the cluster, and removing libraries from the page caused them to stop getting installed on cluster startup. I'm guessing there was some bug causing a disconnect between what the libraries page was showing and what the cluster was actually using to install libraries. I doubt it was anything specific to that cluster (like init scripts, etc.) as we were seeing it on other clusters too.