The problem you ran into was the same one as this thread:
http://groups.google.com/group/rubyonrails-talk/browse_thread/thread/e87b901813a541a5?hl=en
and both are caused by load_application_classes trying to load all
your models at startup. That routine does nothing when
config.cache_classes is false (the default in development mode).
However, I'm surprised that "require 'list'" *ever* worked. Even with
the Rails environment loaded, it gives me an error. The correct
require would be 'active_record/acts/list'.
On a somewhat related note, I've found that Rake tasks work a lot
better than standalone Ruby programs, and save a lot of headaches with
loading the environment...
--Matt Jones