(7.4.z) No ConfigManager instance warning after a quickstart with JSF is undeployed

As soon as a QS that uses JSF (jsonp, temperature-converter and other) is undeployed from EAP CD21 server, a warning appears in the server log:

WARNING [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 84) Unexpected state during contextDestroyed: no ConfigManager instance in current ServletContext but one is expected to exist.

It does not affect the functionality of above-mentioned quickstarts, so I would like to ask whether this warning could be ignored or it deserves a deeper look.