I have seen behavior like this in the past, but in most cases this was because of check-ins that were already in progress on the machines when they were in scope. If there were several policies queued up to run, even after you disable the policy or remove scope to the errant policy as you did, if it had been queued to run on a Mac, it will still actually run when it's time to. At least that's what I've seen.
However, I don't think I've ever seen the policy logs continue to roll in for as long as 24 hours. It's more like for the next hour or two in the cases I recall.
Can you check to see if some of those logs just weren't delayed in being uploaded to the Jamf Pro server? Sometimes policy logs fail to upload for a variety of reasons, and then on next check in, the Mac will upload the logs that it stored locally on the machine, so the timestamps can be off. It usually tells you in the log that the actual execution time was different than the time the log was uploaded though.
