Should an IoC Container obey the Single Responsibility Principle?

I think so. Jeremmy D. Miller has the same opinion here:

"I would think just having any IoC/Dependency Injection tool should be enough out of the box. I wrote another DI tool called StructureMap on sourceforge (predates both Castle and Spring.Net;-)). I haven't added any specific support for NHibernate yet, but it looked like it wasn't really necessary just to be able to handle creating the NHibernate objects from configuration. We use it straight out of the box to locate and create persistence service classes today."

Or an IoC container should be seen as "framework", with several features/responsibilities?