responseConfig produces confusing console warnings [probably a quick fix]

[L3P3]

Using responseConfig on a component produces the following warning:
responsive plugin is deprecated; require "Ext.Responsive" instead
This is probably happening because _ensureResponsivePlugin is still called on all new Components.
Commenting out the call fixes this problem for me.
Shouldn't we just remove that ensureResponsivePlugin thingy or is there another reason for keeping it even after using the plugin is deprecated now? If I remember correctly, responsive props should work without requiring the plugin and in my case, it does that just perfectly.