This behavior is expected with the avf engine. You must use the 'seeknotify' message in this context. From the jit.movie reference:
"The avf backed jit.movie is asynchronous when seeking (e.g. setting the time attribute or using the frame or jump messages). This means that the frame output immediately following a seek request is not guaranteed to be correct. Users requiring exact frame timing must use the seeknotify message output from the object's dump outlet to trigger frame output."