import org.slf4j.LoggerFactory;
import ch.qos.logback.classic.LoggerContext;

((LoggerContext) LoggerFactory.getILoggerFactory()).stop();

The last thing I want is a library that depends only on SLF4J being able to
stop logging because its writer wrongly supposed that application that brings
it in would ever want to log after that point. It's the same error that leads
libraries to try and set logger levels or (worse!) configure their own
appenders.

SLF4J is not an abstraction across all things a logging system might want to
do, it is particularly an abstraction over the concern of sending messages to a
logging system. The fact that it doesn't expose an API to do those other things
is a strength - I know that if I bring in a library that depends only on SLF4J
it won't do anything dumb.