Yes, this is a caching bug.  Thanks for reporting.  We'll look into it.