SOLVED : Filter tables from schema introspection

We have a schema in our Oracle database that has a large number of tables that are created and removed dynamically by the app (on the order of 70,000 tables). This brings introspection to a crawl and makes it nearly impossible to use the table list for that schema. After upgrading to 2016.3 (build #DB-163.7744.4), forgetting schemas and re-synchronizing, it also appears to be causing the UI to become blocked, rendering the Datagrip unresponsive. 

Is there a way to exempt these tables from introspection or to otherwise filter them from the list of tables in the schema explorer sidebar? I attempted to use the object filter under connection properties to do so, matching on the table name w/ a wildcard, but they are still showing up in the list.