Where is the module registry stored outside the database?
Common causes:


External cache (Memcache, etc) that is not purged on rebuild
Your SQL import contains cache from prod (I tend to make sure backups make cache tables structure-only).
Your SQL is imported into a DB which contains tables, but does not drop some of them (such as cache). (I personally drop and create the DB before each import).
The module is still enabled/present in the system table (confirm in your SQL that the row in the system table is gone/disabled &amp; uninstalled).
Something else on your site depends on it and is re-enabling it (eg master module, feature dependencies, etc (although dependencies usually block things from being disabled)).
Sometimes worth doing a drush cc drush after importing the SQL. When in doubt, clear caches ;)