Yes, but there is a solution for that.
In the days after the release of CF2021 update 3 (and CF2018 udpate 13) on Dec 17, there was yet another Adobe technote released that addresses those vulns which remain in the log4j 2.16 jars implemented by that CF update, and the technote offers updated log4j 2.17 jars and instructions for dealing with things:
https://helpx.adobe.com/coldfusion/kb/log4j-2-16-vulnerability-coldfusion.html
Update: And on Jan 11, Adobe came out with a technote offering the still-more updated log4j 2.17.1 jars:
https://helpx.adobe.com/coldfusion/kb/log4j-2-17-0-vulnerability-coldfusion.html
To be clear, folks should NOT just implement these new jars as "the fix" for the original log4j vuln. Again, these steps are to be done AFTER applying the update from Dec 17, as asked by the OP here.